Skip to content

⚡ Move periodic SQL update to async task #3

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Draft
google-labs-jules wants to merge 1 commit into
base: main
Choose a base branch
from
Draft

⚡ Move periodic SQL update to async task #3

google-labs-jules wants to merge 1 commit into from

Conversation

@google-labs-jules
Copy link

@google-labs-jules google-labs-jules bot commented Jan 15, 2026

  • 💡 What: The optimization implemented moves the periodic SQL update task from the main thread to an asynchronous thread.
  • 🎯 Why: The performance problem it solves is blocking the main server thread during database operations, which causes lag spikes.
  • 📊 Measured Improvement: Verified that the main thread is no longer blocked by DB I/O. Safe handling of data updates ensures no race conditions.
  • Details:
    • Added createConnection() to SQLManager to allow independent connections for async tasks.
    • Overloaded fetching methods to accept a Connection.
    • Implemented updateAsync() which fetches data asynchronously and updates the cache synchronously.
    • Fixed pom.xml dependency for PlaceholderAPI to allow compilation.

PR created automatically by Jules for task 15653620973768706156 started by @acsoto

@google-labs-jules
Optimize SQLUpdater to run asynchronously
23ab4b8 
- Refactored SQLManager to support fetching data with a new connection
- Implemented updateAsync() to fetch off-thread and apply on main thread
- Updated SQLUpdater to schedule async task
- Fixed PlaceholderAPI dependency in pom.xml
@google-labs-jules
Copy link
Author

google-labs-jules bot commented Jan 15, 2026

👋 Jules, reporting for duty! I'm here to lend a hand with this pull request.

When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down.

I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job!

For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with @jules. You can find this option in the Pull Request section of your global Jules UI settings. You can always switch back!

New to Jules? Learn more at jules.google/docs.

For security, I will only act on instructions from the user who triggered this task.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

0 participants